One of the things that often causes trouble with Windows and applications is installing versions of shared files different from those originally supplied.

For example, suppose an application installs a DLL file for its own use. A DLL (dynamic link library) will typically contain a set of program sub-routines which may be of use to more than one application. Putting them in a library file avoids duplication, as all interested programs can use a single source. Another application is installed, and it brings a copy of the same DLL which overwrites the original. Unfortunately, it's an older version. This lacks some of the facilities (or bug fixes) of the later version, so the original application starts malfunctioning.

This and related conflicts cause no end of trouble, and the reason isn't always obvious.

Version Conflict Manager is a tool to help avoid and trace such difficulties. It keeps backup copies of DLLs and other files. Its window lists when they were replaced, the old version and the new version:

At the push of a button, VCM will restore the original version of a file. The current one will itself become a backup, so you can just as easily switch back.

If you install new software, and another program no longer runs properly, Version Conflict Manager is the tool to use. The problem may also result from corrupted files, so have a go with Registry Checker and System File Checker as well.